home *** CD-ROM | disk | FTP | other *** search
- Path: idir.net!usenet
- From: Brent DeShazer <mats29@idir.net>
- Newsgroups: comp.lang.c++
- Subject: Re: MFC or OWL?
- Date: Tue, 26 Mar 1996 10:30:38 -0600
- Organization: Mid-America Technology Solutions
- Message-ID: <31581BAE.E5E@idir.net>
- References: <DKKv8H.K35@iquest.net> <4i8od1$clt@Steinlager.tip.net> <4ipmh6$79g@btree.brooktree.com> <1996Mar25.132903.546@friend.kastle.com> <bastion1-2503961918000001@10.0.2.15>
- NNTP-Posting-Host: port54.idtslw1.idir.net
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 2.01 (Win95; I)
-
- >
- > Um, no. BC++ 5.0 can compile MFC stuff, but they do not actually include
- > the MFC. MS' licensing is too restrictive to allow that. I still stand by
-
- Borland tried, from what I understand, and MS said no...
-
- > my earlier assertion that OWL is a significantly higher quality C++
- > framework than MFC, and I'll choose quality over quantity any day.
- >
- > Greg
-
- I'm new to this discussion, but I have to agree with Greg, here. I am quite
- pleased with BC++ 5.0 and OWL 2.0, and see no reason to switch. I just hope Borland
- doesn't cave in the way most other software developers are and work out some arrangement
- for an MFC-only BC++.
- Only gripe about BC++ 5.0 is that I was forced to install Windows95 in order to
- use it. My primary machine is a notebook, so NT was out. Amazingly, however, the 95
- upgrade went smoothly and only took a few hours.
- Brent
-